Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe changes introduce a new Ecosystem section to the documentation. A navigation item is added in the VitePress configuration, and a corresponding Ecosystem markdown file is created. The markdown page includes introductory details along with tables listing Starter Kits and Tools relevant to the project ecosystem. Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant B as Browser
participant C as VitePress Config
participant E as Ecosystem Page
U->>B: Load the website
B->>C: Retrieve navigation configuration
C-->>B: Return list of navigation items (incl. Ecosystem)
U->>B: Click on "Ecosystem" link
B->>E: Request Ecosystem documentation
E-->>B: Serve Ecosystem page content
B-->>U: Render Ecosystem documentation
Poem
Tip ⚡💬 Agentic Chat (Pro Plan, General Availability)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
More templates
@orpc/arktype
@orpc/client
@orpc/contract
@orpc/openapi
@orpc/openapi-client
@orpc/react-query
@orpc/react
@orpc/server
@orpc/shared
@orpc/solid-query
@orpc/standard-server
@orpc/standard-server-fetch
@orpc/standard-server-node
@orpc/svelte-query
@orpc/valibot
@orpc/vue-colada
@orpc/vue-query
@orpc/zod
commit: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
apps/content/docs/ecosystem.md (2)
8-10: Consider making the GitHub link more maintainableWhile the direct edit link is helpful for contributions, consider using a more generic link that doesn't hardcode the branch name (currently "main"). This would make the documentation more maintainable across branch changes.
- If your project is missing here, please [open a PR](https://github.com/unnoq/orpc/edit/main/apps/content/docs/ecosystem.md) to add it. + If your project is missing here, please [open a PR](https://github.com/unnoq/orpc/blob/HEAD/apps/content/docs/ecosystem.md) to add it.
1-23: Consider adding placeholders for future community contributionsSince this is a newly created ecosystem page with just one entry in each section, consider adding a note encouraging specific types of contributions that would be valuable to the ecosystem, or mentioning that more projects will be added as the community grows.
You could add something like:
## Community As the oRPC ecosystem grows, we welcome contributions in the following areas: - Client implementations for additional frameworks - Utility libraries that extend oRPC's functionality - Example projects showing oRPC in real-world applications If you're working on something related to oRPC, please share it by adding it to this page!
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
apps/content/.vitepress/config.ts(1 hunks)apps/content/docs/ecosystem.md(1 hunks)
🔇 Additional comments (4)
apps/content/.vitepress/config.ts (1)
168-168: LGTM: Well-placed ecosystem link in the sidebarThe addition of the ecosystem link in the "Others" section is well-placed and follows the existing navigation pattern consistently. This provides good discoverability for the new ecosystem documentation.
apps/content/docs/ecosystem.md (3)
1-4: LGTM: Clear frontmatter with appropriate title and descriptionThe frontmatter is correctly formatted with a descriptive title and concise description that accurately represents the page's content.
14-16: LGTM: Well-structured Starter Kits tableThe table structure is clear and provides valuable information about each starter kit. The inclusion of GitHub stars adds credibility to the listed projects.
20-22: LGTM: Informative Tools tableThe tools table follows the same clear structure as the Starter Kits table, providing consistent information across the ecosystem page.
1 participant
Summary by CodeRabbit